Deploying and Implementing Enterprise Policies That Control Augmented Reality Computing Functions

ABSTRACT

Methods, systems, and computer-readable media for deploying and implementing enterprise policies that control augmented reality computing functions are presented. A computing device may receive policy information defining policies that, when implemented, control capture of augmented renderings. After receiving the policy information, the computing device may intercept a request to capture at least one view having at least one augmented reality element. In response to intercepting the request, the computing device may determine whether the policies allow capture of views comprising augmented reality elements. Based on determining that the policies allow capture, the computing device may store view information associated with the at least one view having the at least one augmented reality element. Based on determining that the policies do not allow capture, the computing device may prevent the at least one view having the at least one augmented reality element from being captured.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to, and is a continuation of,U.S. patent application Ser. No. 16/239,623, filed on Jan. 4, 2019,which is incorporated herein by reference in its entirety.

FIELD

Aspects of the disclosure relate to computer hardware and software. Inparticular, one or more aspects of the disclosure relate to deployingand implementing enterprise policies that control augmented realitycomputing functions.

BACKGROUND

Enterprise organizations, their employees, and other associated usersare increasingly using mobile computing devices to engage in a varietyof functions, such as sending and receiving email, managing calendarsand tasks, creating and viewing content, accessing and modifyingenterprise information, and executing other functions. As such mobiledevices are increasingly adopted and used, it is increasingly importantfor organizations to control and/or otherwise manage how such devicesare used and/or what information they can access so as to protect thesafety and security of enterprise information and other enterpriseresources. In some instances, however, this may present technicalchallenges.

SUMMARY

Aspects of the disclosure provide technical solutions that may addressand overcome one or more technical challenges associated withcontrolling and/or managing access to enterprise information and otherenterprise resources by mobile devices and/or mobile applications.

In particular, one or more aspects of the disclosure provide ways ofdeploying and implementing enterprise policies that control augmentedreality computing functions. For example, by implementing one or moreaspects of the disclosure, one or more managed application policies maybe defined and enforced, and such policies may control what content iscaptured when a request for a screenshot and/or a video recording isreceived on an augmented reality computing device and/or a spatialcomputing device. For instance, in various circumstances, the policiesmay allow capture of no content at all, real world elements only, meshelements only, augmented elements only, and/or combinations of theseand/or other elements. In addition, in instances where a device'splatform software development kit does not provide built-infunctionality to render mesh elements and/or augmented elements, anenterprise mobility management (EMM) system and/or a rendering serviceassociated with a unified endpoint management (UEM) system may, via itsinjection mechanism, render such content locally and/or in the cloud.

In accordance with one or more embodiments, an enterprise user computingdevice having at least one processor, a communication interface, andmemory may receive, via the communication interface, enterprise policyinformation defining one or more enterprise policies that, whenimplemented, control capture of one or more augmented renderings on theenterprise user computing device. After receiving the enterprise policyinformation defining the one or more enterprise policies, the enterpriseuser computing device may intercept a request to capture at least oneview presented by the enterprise user computing device, and the at leastone view may include at least one augmented reality element. In responseto intercepting the request to capture the at least one view presentedby the enterprise user computing device, the enterprise user computingdevice may determine whether the one or more enterprise policies allowcapture of views comprising augmented reality elements. Based ondetermining that the one or more enterprise policies allow capture ofviews comprising augmented reality elements, the enterprise usercomputing device may store view information associated with the at leastone view having the at least one augmented reality element. Based ondetermining that the one or more enterprise policies do not allowcapture of views comprising augmented reality elements, the enterpriseuser computing device may prevent the at least one view having the atleast one augmented reality element from being captured.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receiving theenterprise policy information defining the one or more enterprisepolicies from an endpoint management computing platform that manages apolicy deployment associated with an enterprise organization.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, prohibits capture of at least one augmented rendering onthe enterprise user computing device.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, prohibits capture of real-world elements associated with atleast one augmented rendering on the enterprise user computing device.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, prohibits capture of augmented elements associated with atleast one augmented rendering on the enterprise user computing device.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, allows capture of mesh elements associated with at leastone augmented rendering on the enterprise user computing device.

In some embodiments, intercepting the request to capture the at leastone view presented by the enterprise user computing device may includeintercepting the request to capture the at least one view presented bythe enterprise user computing device from an operating system executingon the enterprise user computing device.

In some embodiments, intercepting the request to capture the at leastone view presented by the enterprise user computing device may includeintercepting the request to capture the at least one view presented bythe enterprise user computing device from an enterprise applicationexecuting on the enterprise user computing device.

In some embodiments, storing the view information associated with the atleast one view having the at least one augmented reality element mayinclude: generating a modified view based on the at least one viewpresented by the enterprise user computing device; and storinginformation associated with the modified view generated based on the atleast one view presented by the enterprise user computing device. Insome embodiments, generating the modified view based on the at least oneview presented by the enterprise user computing device may includeremoving one or more real-world elements from the at least one viewpresented by the enterprise user computing device. In some embodiments,generating the modified view based on the at least one view presented bythe enterprise user computing device may include removing one or moreaugmented elements from the at least one view presented by theenterprise user computing device.

In some embodiments, preventing the at least one view comprising the atleast one augmented reality element from being captured may include:generating an error notification indicating that the one or moreenterprise policies do not allow capture of views comprising augmentedreality elements; and presenting the error notification indicating thatthe one or more enterprise policies do not allow capture of viewscomprising augmented reality elements.

In some embodiments, prior to storing the view information associatedwith the at least one view comprising the at least one augmented realityelement, the enterprise user computing device may render one or moremesh elements associated with the at least one view presented by theenterprise user computing device. Subsequently, the enterprise usercomputing device may merge the one or more mesh elements associated withthe at least one view presented by the enterprise user computing devicewith image data defining the at least one view presented by theenterprise user computing device to produce the view informationassociated with the at least one view comprising the at least oneaugmented reality element.

In some embodiments, prior to storing the view information associatedwith the at least one view comprising the at least one augmented realityelement, the enterprise user computing device may send, via thecommunication interface, to a rendering service computing platform, arequest for rendered mesh information associated with the at least oneview presented by the enterprise user computing device. Subsequently,the enterprise user computing device may receive, via the communicationinterface, from the rendering service computing platform, meshinformation defining one or more mesh elements associated with the atleast one view presented by the enterprise user computing device. Then,the enterprise user computing device may merge the mesh informationdefining the one or more mesh elements associated with the at least oneview presented by the enterprise user computing device with image datadefining the at least one view presented by the enterprise usercomputing device to produce the view information associated with the atleast one view comprising the at least one augmented reality element.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative computer system architecture that may beused in accordance with one or more illustrative aspects describedherein.

FIG. 2 depicts an illustrative remote-access system architecture thatmay be used in accordance with one or more illustrative aspectsdescribed herein.

FIG. 3 depicts an illustrative virtualized (hypervisor) systemarchitecture that may be used in accordance with one or moreillustrative aspects described herein.

FIG. 4 depicts an illustrative cloud-based system architecture that maybe used in accordance with one or more illustrative aspects describedherein.

FIG. 5 depicts an illustrative enterprise mobility management system inaccordance with one or more illustrative aspects described herein.

FIG. 6 depicts another illustrative enterprise mobility managementsystem in accordance with one or more illustrative aspects describedherein.

FIG. 7 depicts an illustrative computing environment for deploying andimplementing enterprise policies that control augmented realitycomputing functions in accordance with one or more illustrative aspectsdescribed herein.

FIGS. 8A-8C depict an example event sequence for deploying andimplementing enterprise policies that control augmented realitycomputing functions in accordance with one or more illustrative aspectsdescribed herein.

FIGS. 9-14 depict example graphical user interfaces for deploying andimplementing enterprise policies that control augmented realitycomputing functions in accordance with one or more illustrative aspectsdescribed herein.

FIG. 15 depicts an example method of deploying and implementingenterprise policies that control augmented reality computing functionsin accordance with one or more illustrative aspects described herein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

As an introduction to subject matter described below, aspects of thedisclosure relate to deploying and implementing enterprise policies thatcontrol augmented reality computing functions. For example, anenterprise organization may wish to implement a policy that disablesscreenshots in applications that are managed by an enterprise mobilitymanagement (EMM) system and/or a unified endpoint management (UEM)system. For instance, such applications may be enterprise applicationsthat may display sensitive information, and the enterprise organizationmay wish to restrict users of the application and/or the device fromtaking a screenshot or capturing a video recording of the screen.

When addressing augmented reality and/or spatial computing platforms, anenterprise organization may have similar concerns about screenshotsand/or video recordings, but different issues and/or nuances may arise.For instance, an enterprise organization might not want any real-worldelements to be captured in such a screenshot or video recording, becausesuch elements might reveal internal details of the organization'soperations or present a privacy risk to the end user; but theorganization might not be concerned about augmented reality elementsincluded in a view being captured. Alternatively, the organization mightnot be concerned about real-world elements being captured and insteadmay wish that augmented-reality elements be stripped out. Further still,the organization may have preferences about whether a mesh associatedwith an augmented view can be captured, as such a mesh may representand/or correspond to an outline of real-world elements in a view and mayenable an augmented reality and/or spatial computing device to determinewhere solid surfaces are and present overlays accordingly. As usedherein, the terms “augmented reality” and “spatial computing” may beused interchangeable and may refer to computing devices and/or computingfunctionality that enables a device to take a view of real-worldelements, recognize solid objects within the view, create and/or load amesh of such solid objects, and then add virtual objects and/or imagesinto the view that interact with the mesh.

Computing Architecture

Computer software, hardware, and networks may be utilized in a varietyof different system environments, including standalone, networked,remote-access (also known as remote desktop), virtualized, and/orcloud-based environments, among others. FIG. 1 illustrates one exampleof a system architecture and data processing device that may be used toimplement one or more illustrative aspects described herein in astandalone and/or networked environment. Various network nodes 103, 105,107, and 109 may be interconnected via a wide area network (WAN) 101,such as the Internet. Other networks may also or alternatively be used,including private intranets, corporate networks, local area networks(LAN), metropolitan area networks (MAN), wireless networks, personalnetworks (PAN), and the like. Network 101 is for illustration purposesand may be replaced with fewer or additional computer networks. A localarea network 133 may have one or more of any known LAN topology and mayuse one or more of a variety of different protocols, such as Ethernet.Devices 103, 105, 107, and 109 and other devices (not shown) may beconnected to one or more of the networks via twisted pair wires, coaxialcable, fiber optics, radio waves, or other communication media.

The term “network” as used herein and depicted in the drawings refersnot only to systems in which remote storage devices are coupled togethervia one or more communication paths, but also to stand-alone devicesthat may be coupled, from time to time, to such systems that havestorage capability. Consequently, the term “network” includes not only a“physical network” but also a “content network,” which is comprised ofthe data—attributable to a single entity—which resides across allphysical networks.

The components may include data server 103, web server 105, and clientcomputers 107, 109. Data server 103 provides overall access, control andadministration of databases and control software for performing one ormore illustrative aspects describe herein. Data server 103 may beconnected to web server 105 through which users interact with and obtaindata as requested. Alternatively, data server 103 may act as a webserver itself and be directly connected to the Internet. Data server 103may be connected to web server 105 through the local area network 133,the wide area network 101 (e.g., the Internet), via direct or indirectconnection, or via some other network. Users may interact with the dataserver 103 using remote computers 107, 109, e.g., using a web browser toconnect to the data server 103 via one or more externally exposed websites hosted by web server 105. Client computers 107, 109 may be used inconcert with data server 103 to access data stored therein, or may beused for other purposes. For example, from client device 107 a user mayaccess web server 105 using an Internet browser, as is known in the art,or by executing a software application that communicates with web server105 and/or data server 103 over a computer network (such as theInternet).

Servers and applications may be combined on the same physical machines,and retain separate virtual or logical addresses, or may reside onseparate physical machines. FIG. 1 illustrates just one example of anetwork architecture that may be used, and those of skill in the artwill appreciate that the specific network architecture and dataprocessing devices used may vary, and are secondary to the functionalitythat they provide, as further described herein. For example, servicesprovided by web server 105 and data server 103 may be combined on asingle server.

Each component 103, 105, 107, 109 may be any type of known computer,server, or data processing device. Data server 103, e.g., may include aprocessor 111 controlling overall operation of the data server 103. Dataserver 103 may further include random access memory (RAM) 113, read onlymemory (ROM) 115, network interface 117, input/output interfaces 119(e.g., keyboard, mouse, display, printer, etc.), and memory 121.Input/output (I/O) 119 may include a variety of interface units anddrives for reading, writing, displaying, and/or printing data or files.Memory 121 may further store operating system software 123 forcontrolling overall operation of the data processing device 103, controllogic 125 for instructing data server 103 to perform aspects describedherein, and other application software 127 providing secondary, support,and/or other functionality which may or might not be used in conjunctionwith aspects described herein. The control logic 125 may also bereferred to herein as the data server software 125. Functionality of thedata server software 125 may refer to operations or decisions madeautomatically based on rules coded into the control logic 125, mademanually by a user providing input into the system, and/or a combinationof automatic processing based on user input (e.g., queries, dataupdates, etc.).

Memory 121 may also store data used in performance of one or moreaspects described herein, including a first database 129 and a seconddatabase 131. In some embodiments, the first database 129 may includethe second database 131 (e.g., as a separate table, report, etc.). Thatis, the information can be stored in a single database, or separatedinto different logical, virtual, or physical databases, depending onsystem design. Devices 105, 107, and 109 may have similar or differentarchitecture as described with respect to device 103. Those of skill inthe art will appreciate that the functionality of data processing device103 (or device 105, 107, or 109) as described herein may be spreadacross multiple data processing devices, for example, to distributeprocessing load across multiple computers, to segregate transactionsbased on geographic location, user access level, quality of service(QoS), etc.

One or more aspects may be embodied in computer-usable or readable dataand/or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices as describedherein. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other device. The modules may be written in a source codeprogramming language that is subsequently compiled for execution, or maybe written in a scripting language such as (but not limited to)HyperText Markup Language (HTML) or Extensible Markup Language (XML).The computer executable instructions may be stored on a computerreadable medium such as a nonvolatile storage device. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various transmission (non-storage)media representing data or events as described herein may be transferredbetween a source and a destination in the form of electromagnetic wavestraveling through signal-conducting media such as metal wires, opticalfibers, and/or wireless transmission media (e.g., air and/or space).Various aspects described herein may be embodied as a method, a dataprocessing system, or a computer program product. Therefore, variousfunctionalities may be embodied in whole or in part in software,firmware, and/or hardware or hardware equivalents such as integratedcircuits, field programmable gate arrays (FPGA), and the like.Particular data structures may be used to more effectively implement oneor more aspects described herein, and such data structures arecontemplated within the scope of computer executable instructions andcomputer-usable data described herein.

With further reference to FIG. 2, one or more aspects described hereinmay be implemented in a remote-access environment. FIG. 2 depicts anexample system architecture including a computing device 201 in anillustrative computing environment 200 that may be used according to oneor more illustrative aspects described herein. Computing device 201 maybe used as a server 206 a in a single-server or multi-server desktopvirtualization system (e.g., a remote access or cloud system) and can beconfigured to provide virtual machines for client access devices. Thecomputing device 201 may have a processor 203 for controlling overalloperation of the device 201 and its associated components, including RAM205, ROM 207, Input/Output (I/O) module 209, and memory 215.

I/O module 209 may include a mouse, keypad, touch screen, scanner,optical reader, and/or stylus (or other input device(s)) through which auser of computing device 201 may provide input, and may also include oneor more of a speaker for providing audio output and one or more of avideo display device for providing textual, audiovisual, and/orgraphical output. Software may be stored within memory 215 and/or otherstorage to provide instructions to processor 203 for configuringcomputing device 201 into a special purpose computing device in order toperform various functions as described herein. For example, memory 215may store software used by the computing device 201, such as anoperating system 217, application programs 219, and an associateddatabase 221.

Computing device 201 may operate in a networked environment supportingconnections to one or more remote computers, such as terminals 240 (alsoreferred to as client devices). The terminals 240 may be personalcomputers, mobile devices, laptop computers, tablets, or servers thatinclude many or all of the elements described above with respect to thecomputing device 103 or 201. The network connections depicted in FIG. 2include a local area network (LAN) 225 and a wide area network (WAN)229, but may also include other networks. When used in a LAN networkingenvironment, computing device 201 may be connected to the LAN 225through a network interface or adapter 223. When used in a WANnetworking environment, computing device 201 may include a modem orother wide area network interface 227 for establishing communicationsover the WAN 229, such as computer network 230 (e.g., the Internet). Itwill be appreciated that the network connections shown are illustrativeand other means of establishing a communications link between thecomputers may be used. Computing device 201 and/or terminals 240 mayalso be mobile terminals (e.g., mobile phones, smartphones, personaldigital assistants (PDAs), notebooks, etc.) including various othercomponents, such as a battery, speaker, and antennas (not shown).

Aspects described herein may also be operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of other computing systems, environments,and/or configurations that may be suitable for use with aspectsdescribed herein include, but are not limited to, personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network personal computers (PCs), minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

As shown in FIG. 2, one or more client devices 240 may be incommunication with one or more servers 206 a-206 n (generally referredto herein as “server(s) 206”). In one embodiment, the computingenvironment 200 may include a network appliance installed between theserver(s) 206 and client machine(s) 240. The network appliance maymanage client/server connections, and in some cases can load balanceclient connections amongst a plurality of backend servers 206.

The client machine(s) 240 may in some embodiments be referred to as asingle client machine 240 or a single group of client machines 240,while server(s) 206 may be referred to as a single server 206 or asingle group of servers 206. In one embodiment a single client machine240 communicates with more than one server 206, while in anotherembodiment a single server 206 communicates with more than one clientmachine 240. In yet another embodiment, a single client machine 240communicates with a single server 206.

A client machine 240 can, in some embodiments, be referenced by any oneof the following non-exhaustive terms: client machine(s); client(s);client computer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); or endpointnode(s). The server 206, in some embodiments, may be referenced by anyone of the following non-exhaustive terms: server(s), local machine;remote machine; server farm(s), or host computing device(s).

In one embodiment, the client machine 240 may be a virtual machine. Thevirtual machine may be any virtual machine, while in some embodimentsthe virtual machine may be any virtual machine managed by a Type 1 orType 2 hypervisor, for example, a hypervisor developed by CitrixSystems, IBM, VMware, or any other hypervisor. In some aspects, thevirtual machine may be managed by a hypervisor, while in other aspectsthe virtual machine may be managed by a hypervisor executing on a server206 or a hypervisor executing on a client 240.

Some embodiments include a client device 240 that displays applicationoutput generated by an application remotely executing on a server 206 orother remotely located machine. In these embodiments, the client device240 may execute a virtual machine receiver program or application todisplay the output in an application window, a browser, or other outputwindow. In one example, the application is a desktop, while in otherexamples the application is an application that generates or presents adesktop. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications, as used herein, areprograms that execute after an instance of an operating system (and,optionally, also the desktop) has been loaded.

The server 206, in some embodiments, uses a remote presentation protocolor other program to send data to a thin-client or remote-displayapplication executing on the client to present display output generatedby an application executing on the server 206. The thin-client orremote-display protocol can be any one of the following non-exhaustivelist of protocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

A remote computing environment may include more than one server 206a-206 n such that the servers 206 a-206 n are logically grouped togetherinto a server farm 206, for example, in a cloud computing environment.The server farm 206 may include servers 206 that are geographicallydispersed while logically grouped together, or servers 206 that arelocated proximate to each other while logically grouped together.Geographically dispersed servers 206 a-206 n within a server farm 206can, in some embodiments, communicate using a WAN (wide), MAN(metropolitan), or LAN (local), where different geographic regions canbe characterized as: different continents; different regions of acontinent; different countries; different states; different cities;different campuses; different rooms; or any combination of the precedinggeographical locations. In some embodiments the server farm 206 may beadministered as a single entity, while in other embodiments the serverfarm 206 can include multiple server farms.

In some embodiments, a server farm may include servers 206 that executea substantially similar type of operating system platform (e.g.,WINDOWS, UNIX, LINUX, iOS, ANDROID, SYMBIAN, etc.) In other embodiments,server farm 206 may include a first group of one or more servers thatexecute a first type of operating system platform, and a second group ofone or more servers that execute a second type of operating systemplatform.

Server 206 may be configured as any type of server, as needed, e.g., afile server, an application server, a web server, a proxy server, anappliance, a network appliance, a gateway, an application gateway, agateway server, a virtualization server, a deployment server, a SecureSockets Layer (SSL) VPN server, a firewall, a web server, an applicationserver or as a master application server, a server executing an activedirectory, or a server executing an application acceleration programthat provides firewall functionality, application functionality, or loadbalancing functionality. Other server types may also be used.

Some embodiments include a first server 206 a that receives requestsfrom a client machine 240, forwards the request to a second server 206 b(not shown), and responds to the request generated by the client machine240 with a response from the second server 206 b (not shown.) Firstserver 206 a may acquire an enumeration of applications available to theclient machine 240 as well as address information associated with anapplication server 206 hosting an application identified within theenumeration of applications. First server 206 a can then present aresponse to the client's request using a web interface, and communicatedirectly with the client 240 to provide the client 240 with access to anidentified application. One or more clients 240 and/or one or moreservers 206 may transmit data over network 230, e.g., network 101.

FIG. 3 shows a high-level architecture of an illustrative desktopvirtualization system. As shown, the desktop virtualization system maybe single-server or multi-server system, or cloud system, including atleast one virtualization server 301 configured to provide virtualdesktops and/or virtual applications to one or more client accessdevices 240. As used herein, a desktop refers to a graphical environmentor space in which one or more applications may be hosted and/orexecuted. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications may include programsthat execute after an instance of an operating system (and, optionally,also the desktop) has been loaded. Each instance of the operating systemmay be physical (e.g., one operating system per device) or virtual(e.g., many instances of an OS running on a single device). Eachapplication may be executed on a local device, or executed on a remotelylocated device (e.g., remoted).

A computer device 301 may be configured as a virtualization server in avirtualization environment, for example, a single-server, multi-server,or cloud computing environment. Virtualization server 301 illustrated inFIG. 3 can be deployed as and/or implemented by one or more embodimentsof the server 206 illustrated in FIG. 2 or by other known computingdevices. Included in virtualization server 301 is a hardware layer thatcan include one or more physical disks 304, one or more physical devices306, one or more physical processors 308, and one or more physicalmemories 316. In some embodiments, firmware 312 can be stored within amemory element in the physical memory 316 and can be executed by one ormore of the physical processors 308. Virtualization server 301 mayfurther include an operating system 314 that may be stored in a memoryelement in the physical memory 316 and executed by one or more of thephysical processors 308. Still further, a hypervisor 302 may be storedin a memory element in the physical memory 316 and can be executed byone or more of the physical processors 308.

Executing on one or more of the physical processors 308 may be one ormore virtual machines 332A-C (generally 332). Each virtual machine 332may have a virtual disk 326A-C and a virtual processor 328A-C. In someembodiments, a first virtual machine 332A may execute, using a virtualprocessor 328A, a control program 320 that includes a tools stack 324.Control program 320 may be referred to as a control virtual machine,Dom0, Domain 0, or other virtual machine used for system administrationand/or control. In some embodiments, one or more virtual machines 332B-Ccan execute, using a virtual processor 328B-C, a guest operating system330A-B.

Virtualization server 301 may include a hardware layer 310 with one ormore pieces of hardware that communicate with the virtualization server301. In some embodiments, the hardware layer 310 can include one or morephysical disks 304, one or more physical devices 306, one or morephysical processors 308, and one or more physical memory 316. Physicalcomponents 304, 306, 308, and 316 may include, for example, any of thecomponents described above. Physical devices 306 may include, forexample, a network interface card, a video card, a keyboard, a mouse, aninput device, a monitor, a display device, speakers, an optical drive, astorage device, a universal serial bus connection, a printer, a scanner,a network element (e.g., router, firewall, network address translator,load balancer, virtual private network (VPN) gateway, Dynamic HostConfiguration Protocol (DHCP) router, etc.), or any device connected toor communicating with virtualization server 301. Physical memory 316 inthe hardware layer 310 may include any type of memory. Physical memory316 may store data, and in some embodiments may store one or moreprograms, or set of executable instructions. FIG. 3 illustrates anembodiment where firmware 312 is stored within the physical memory 316of virtualization server 301. Programs or executable instructions storedin the physical memory 316 can be executed by the one or more processors308 of virtualization server 301.

Virtualization server 301 may also include a hypervisor 302. In someembodiments, hypervisor 302 may be a program executed by processors 308on virtualization server 301 to create and manage any number of virtualmachines 332. Hypervisor 302 may be referred to as a virtual machinemonitor, or platform virtualization software. In some embodiments,hypervisor 302 can be any combination of executable instructions andhardware that monitors virtual machines executing on a computingmachine. Hypervisor 302 may be Type 2 hypervisor, where the hypervisorexecutes within an operating system 314 executing on the virtualizationserver 301. Virtual machines may then execute at a level above thehypervisor 302. In some embodiments, the Type 2 hypervisor may executewithin the context of a user's operating system such that the Type 2hypervisor interacts with the user's operating system. In otherembodiments, one or more virtualization servers 301 in a virtualizationenvironment may instead include a Type 1 hypervisor (not shown). A Type1 hypervisor may execute on the virtualization server 301 by directlyaccessing the hardware and resources within the hardware layer 310. Thatis, while a Type 2 hypervisor 302 accesses system resources through ahost operating system 314, as shown, a Type 1 hypervisor may directlyaccess all system resources without the host operating system 314. AType 1 hypervisor may execute directly on one or more physicalprocessors 308 of virtualization server 301, and may include programdata stored in the physical memory 316.

Hypervisor 302, in some embodiments, can provide virtual resources tooperating systems 330 or control programs 320 executing on virtualmachines 332 in any manner that simulates the operating systems 330 orcontrol programs 320 having direct access to system resources. Systemresources can include, but are not limited to, physical devices 306,physical disks 304, physical processors 308, physical memory 316, andany other component included in hardware layer 310 of the virtualizationserver 301. Hypervisor 302 may be used to emulate virtual hardware,partition physical hardware, virtualize physical hardware, and/orexecute virtual machines that provide access to computing environments.In still other embodiments, hypervisor 302 may control processorscheduling and memory partitioning for a virtual machine 332 executingon virtualization server 301. Hypervisor 302 may include thosemanufactured by VMWare, Inc., of Palo Alto, Calif.; the XENPROJECThypervisor, an open source product whose development is overseen by theopen source XenProject.org community; HyperV, VirtualServer or virtualPC hypervisors provided by Microsoft, or others. In some embodiments,virtualization server 301 may execute a hypervisor 302 that creates avirtual machine platform on which guest operating systems may execute.In these embodiments, the virtualization server 301 may be referred toas a host server. An example of such a virtualization server is theXENSERVER provided by Citrix Systems, Inc., of Fort Lauderdale, Fla.

Hypervisor 302 may create one or more virtual machines 332B-C (generally332) in which guest operating systems 330 execute. In some embodiments,hypervisor 302 may load a virtual machine image to create a virtualmachine 332. In other embodiments, the hypervisor 302 may execute aguest operating system 330 within virtual machine 332. In still otherembodiments, virtual machine 332 may execute guest operating system 330.

In addition to creating virtual machines 332, hypervisor 302 may controlthe execution of at least one virtual machine 332. In other embodiments,hypervisor 302 may present at least one virtual machine 332 with anabstraction of at least one hardware resource provided by thevirtualization server 301 (e.g., any hardware resource available withinthe hardware layer 310). In other embodiments, hypervisor 302 maycontrol the manner in which virtual machines 332 access physicalprocessors 308 available in virtualization server 301. Controllingaccess to physical processors 308 may include determining whether avirtual machine 332 should have access to a processor 308, and howphysical processor capabilities are presented to the virtual machine332.

As shown in FIG. 3, virtualization server 301 may host or execute one ormore virtual machines 332. A virtual machine 332 is a set of executableinstructions that, when executed by a processor 308, may imitate theoperation of a physical computer such that the virtual machine 332 canexecute programs and processes much like a physical computing device.While FIG. 3 illustrates an embodiment where a virtualization server 301hosts three virtual machines 332, in other embodiments virtualizationserver 301 can host any number of virtual machines 332. Hypervisor 302,in some embodiments, may provide each virtual machine 332 with a uniquevirtual view of the physical hardware, memory, processor, and othersystem resources available to that virtual machine 332. In someembodiments, the unique virtual view can be based on one or more ofvirtual machine permissions, application of a policy engine to one ormore virtual machine identifiers, a user accessing a virtual machine,the applications executing on a virtual machine, networks accessed by avirtual machine, or any other desired criteria. For instance, hypervisor302 may create one or more unsecure virtual machines 332 and one or moresecure virtual machines 332. Unsecure virtual machines 332 may beprevented from accessing resources, hardware, memory locations, andprograms that secure virtual machines 332 may be permitted to access. Inother embodiments, hypervisor 302 may provide each virtual machine 332with a substantially similar virtual view of the physical hardware,memory, processor, and other system resources available to the virtualmachines 332.

Each virtual machine 332 may include a virtual disk 326A-C (generally326) and a virtual processor 328A-C (generally 328.) The virtual disk326, in some embodiments, is a virtualized view of one or more physicaldisks 304 of the virtualization server 301, or a portion of one or morephysical disks 304 of the virtualization server 301. The virtualizedview of the physical disks 304 can be generated, provided, and managedby the hypervisor 302. In some embodiments, hypervisor 302 provides eachvirtual machine 332 with a unique view of the physical disks 304. Thus,in these embodiments, the particular virtual disk 326 included in eachvirtual machine 332 can be unique when compared with the other virtualdisks 326.

A virtual processor 328 can be a virtualized view of one or morephysical processors 308 of the virtualization server 301. In someembodiments, the virtualized view of the physical processors 308 can begenerated, provided, and managed by hypervisor 302. In some embodiments,virtual processor 328 has substantially all of the same characteristicsof at least one physical processor 308. In other embodiments, virtualprocessor 308 provides a modified view of physical processors 308 suchthat at least some of the characteristics of the virtual processor 328are different than the characteristics of the corresponding physicalprocessor 308.

With further reference to FIG. 4, some aspects described herein may beimplemented in a cloud-based environment. FIG. 4 illustrates an exampleof a cloud computing environment (or cloud system) 400. As seen in FIG.4, client computers 411-414 may communicate with a cloud managementserver 410 to access the computing resources (e.g., host servers 403a-403 b (generally referred herein as “host servers 403”), storageresources 404 a-404 b (generally referred herein as “storage resources404”), and network elements 405 a-405 b (generally referred herein as“network resources 405”)) of the cloud system.

Management server 410 may be implemented on one or more physicalservers. The management server 410 may run, for example, CLOUDPLATFORMby Citrix Systems, Inc. of Ft. Lauderdale, Fla., or OPENSTACK, amongothers. Management server 410 may manage various computing resources,including cloud hardware and software resources, for example, hostcomputers 403, data storage devices 404, and networking devices 405. Thecloud hardware and software resources may include private and/or publiccomponents. For example, a cloud may be configured as a private cloud tobe used by one or more particular customers or client computers 411-414and/or over a private network. In other embodiments, public clouds orhybrid public-private clouds may be used by other customers over an openor hybrid networks.

Management server 410 may be configured to provide user interfacesthrough which cloud operators and cloud customers may interact with thecloud system 400. For example, the management server 410 may provide aset of application programming interfaces (APIs) and/or one or morecloud operator console applications (e.g., web-based or standaloneapplications) with user interfaces to allow cloud operators to managethe cloud resources, configure the virtualization layer, manage customeraccounts, and perform other cloud administration tasks. The managementserver 410 also may include a set of APIs and/or one or more customerconsole applications with user interfaces configured to receive cloudcomputing requests from end users via client computers 411-414, forexample, requests to create, modify, or destroy virtual machines withinthe cloud. Client computers 411-414 may connect to management server 410via the Internet or some other communication network, and may requestaccess to one or more of the computing resources managed by managementserver 410. In response to client requests, the management server 410may include a resource manager configured to select and provisionphysical resources in the hardware layer of the cloud system based onthe client requests. For example, the management server 410 andadditional components of the cloud system may be configured toprovision, create, and manage virtual machines and their operatingenvironments (e.g., hypervisors, storage resources, services offered bythe network elements, etc.) for customers at client computers 411-414,over a network (e.g., the Internet), providing customers withcomputational resources, data storage services, networking capabilities,and computer platform and application support. Cloud systems also may beconfigured to provide various specific services, including securitysystems, development environments, user interfaces, and the like.

Certain clients 411-414 may be related, for example, to different clientcomputers creating virtual machines on behalf of the same end user, ordifferent users affiliated with the same company or organization. Inother examples, certain clients 411-414 may be unrelated, such as usersaffiliated with different companies or organizations. For unrelatedclients, information on the virtual machines or storage of any one usermay be hidden from other users.

Referring now to the physical hardware layer of a cloud computingenvironment, availability zones 401-402 (or zones) may refer to acollocated set of physical computing resources. Zones may begeographically separated from other zones in the overall cloud ofcomputing resources. For example, zone 401 may be a first clouddatacenter located in California, and zone 402 may be a second clouddatacenter located in Florida. Management server 410 may be located atone of the availability zones, or at a separate location. Each zone mayinclude an internal network that interfaces with devices that areoutside of the zone, such as the management server 410, through agateway. End users of the cloud (e.g., clients 411-414) might or mightnot be aware of the distinctions between zones. For example, an end usermay request the creation of a virtual machine having a specified amountof memory, processing power, and network capabilities. The managementserver 410 may respond to the user's request and may allocate theresources to create the virtual machine without the user knowing whetherthe virtual machine was created using resources from zone 401 or zone402. In other examples, the cloud system may allow end users to requestthat virtual machines (or other cloud resources) are allocated in aspecific zone or on specific resources 403-405 within a zone.

In this example, each zone 401-402 may include an arrangement of variousphysical hardware components (or computing resources) 403-405, forexample, physical hosting resources (or processing resources), physicalnetwork resources, physical storage resources, switches, and additionalhardware resources that may be used to provide cloud computing servicesto customers. The physical hosting resources in a cloud zone 401-402 mayinclude one or more computer servers 403, such as the virtualizationservers 301 described above, which may be configured to create and hostvirtual machine instances. The physical network resources in a cloudzone 401 or 402 may include one or more network elements 405 (e.g.,network service providers) comprising hardware and/or softwareconfigured to provide a network service to cloud customers, such asfirewalls, network address translators, load balancers, virtual privatenetwork (VPN) gateways, Dynamic Host Configuration Protocol (DHCP)routers, and the like. The storage resources in the cloud zone 401-402may include storage disks (e.g., solid state drives (SSDs), magnetichard disks, etc.) and other storage devices.

The example cloud computing environment shown in FIG. 4 also may includea virtualization layer (e.g., as shown in FIGS. 1-3) with additionalhardware and/or software resources configured to create and managevirtual machines and provide other services to customers using thephysical resources in the cloud. The virtualization layer may includehypervisors, as described above in FIG. 3, along with other componentsto provide network virtualizations, storage virtualizations, etc. Thevirtualization layer may be as a separate layer from the physicalresource layer, or may share some or all of the same hardware and/orsoftware resources with the physical resource layer. For example, thevirtualization layer may include a hypervisor installed in each of thevirtualization servers 403 with the physical computing resources. Knowncloud systems may alternatively be used, e.g., WINDOWS AZURE (MicrosoftCorporation of Redmond Wash.), AMAZON EC2 (Amazon.com Inc. of Seattle,Wash.), IBM BLUE CLOUD (IBM Corporation of Armonk, N.Y.), or others.

Enterprise Mobility Management Architecture

FIG. 5 represents an enterprise mobility technical architecture 500 foruse in a “Bring Your Own Device” (BYOD) environment. The architectureenables a user of a mobile device 502 to both access enterprise orpersonal resources from a mobile device 502 and use the mobile device502 for personal use. The user may access such enterprise resources 504or enterprise services 508 using a mobile device 502 that is purchasedby the user or a mobile device 502 that is provided by the enterprise tothe user. The user may utilize the mobile device 502 for business useonly or for business and personal use. The mobile device 502 may run aniOS operating system, an Android operating system, or the like. Theenterprise may choose to implement policies to manage the mobile device502. The policies may be implemented through a firewall or gateway insuch a way that the mobile device 502 may be identified, secured orsecurity verified, and provided selective or full access to theenterprise resources (e.g., 504 and 508.) The policies may be mobiledevice management policies, mobile application management policies,mobile data management policies, or some combination of mobile device,application, and data management policies. A mobile device 502 that ismanaged through the application of mobile device management policies maybe referred to as an enrolled device.

In some embodiments, the operating system of the mobile device 502 maybe separated into a managed partition 510 and an unmanaged partition512. The managed partition 510 may have policies applied to it to securethe applications running on and data stored in the managed partition510. The applications running on the managed partition 510 may be secureapplications. In other embodiments, all applications may execute inaccordance with a set of one or more policy files received separate fromthe application, and which define one or more security parameters,features, resource restrictions, and/or other access controls that areenforced by the mobile device management system when that application isexecuting on the mobile device 502. By operating in accordance withtheir respective policy file(s), each application may be allowed orrestricted from communications with one or more other applicationsand/or resources, thereby creating a virtual partition. Thus, as usedherein, a partition may refer to a physically partitioned portion ofmemory (physical partition), a logically partitioned portion of memory(logical partition), and/or a virtual partition created as a result ofenforcement of one or more policies and/or policy files across multipleapplications as described herein (virtual partition). Stateddifferently, by enforcing policies on managed applications, thoseapplications may be restricted to only be able to communicate with othermanaged applications and trusted enterprise resources, thereby creatinga virtual partition that is not accessible by unmanaged applications anddevices.

The secure applications may be email applications, web browsingapplications, software-as-a-service (SaaS) access applications, WindowsApplication access applications, and the like. The secure applicationsmay be secure native applications 514, secure remote applications 522executed by a secure application launcher 518, virtualizationapplications 526 executed by a secure application launcher 518, and thelike. The secure native applications 514 may be wrapped by a secureapplication wrapper 520. The secure application wrapper 520 may includeintegrated policies that are executed on the mobile device 502 when thesecure native application 514 is executed on the mobile device 502. Thesecure application wrapper 520 may include meta-data that points thesecure native application 514 running on the mobile device 502 to theresources hosted at the enterprise (e.g., 504 and 508) that the securenative application 514 may require to complete the task requested uponexecution of the secure native application 514. The secure remoteapplications 522 executed by a secure application launcher 518 may beexecuted within the secure application launcher 518. The virtualizationapplications 526 executed by a secure application launcher 518 mayutilize resources on the mobile device 502, at the enterprise resources504, and the like. The resources used on the mobile device 502 by thevirtualization applications 526 executed by a secure applicationlauncher 518 may include user interaction resources, processingresources, and the like. The user interaction resources may be used tocollect and transmit keyboard input, mouse input, camera input, tactileinput, audio input, visual input, gesture input, and the like. Theprocessing resources may be used to present a user interface, processdata received from the enterprise resources 504, and the like. Theresources used at the enterprise resources 504 by the virtualizationapplications 526 executed by a secure application launcher 518 mayinclude user interface generation resources, processing resources, andthe like. The user interface generation resources may be used toassemble a user interface, modify a user interface, refresh a userinterface, and the like. The processing resources may be used to createinformation, read information, update information, delete information,and the like. For example, the virtualization application 526 may recorduser interactions associated with a graphical user interface (GUI) andcommunicate them to a server application where the server applicationwill use the user interaction data as an input to the applicationoperating on the server. In such an arrangement, an enterprise may electto maintain the application on the server side as well as data, files,etc. associated with the application. While an enterprise may elect to“mobilize” some applications in accordance with the principles herein bysecuring them for deployment on the mobile device 502, this arrangementmay also be elected for certain applications. For example, while someapplications may be secured for use on the mobile device 502, othersmight not be prepared or appropriate for deployment on the mobile device502 so the enterprise may elect to provide the mobile user access to theunprepared applications through virtualization techniques. As anotherexample, the enterprise may have large complex applications with largeand complex data sets (e.g., material resource planning applications)where it would be very difficult, or otherwise undesirable, to customizethe application for the mobile device 502 so the enterprise may elect toprovide access to the application through virtualization techniques. Asyet another example, the enterprise may have an application thatmaintains highly secured data (e.g., human resources data, customerdata, engineering data) that may be deemed by the enterprise as toosensitive for even the secured mobile environment so the enterprise mayelect to use virtualization techniques to permit mobile access to suchapplications and data. An enterprise may elect to provide both fullysecured and fully functional applications on the mobile device 502 aswell as a virtualization application 526 to allow access to applicationsthat are deemed more properly operated on the server side. In anembodiment, the virtualization application 526 may store some data,files, etc. on the mobile device 502 in one of the secure storagelocations. An enterprise, for example, may elect to allow certaininformation to be stored on the mobile device 502 while not permittingother information.

In connection with the virtualization application 526, as describedherein, the mobile device 502 may have a virtualization application 526that is designed to present GUIs and then record user interactions withthe GUI. The virtualization application 526 may communicate the userinteractions to the server side to be used by the server sideapplication as user interactions with the application. In response, theapplication on the server side may transmit back to the mobile device502 a new GUI. For example, the new GUI may be a static page, a dynamicpage, an animation, or the like, thereby providing access to remotelylocated resources.

The secure applications 514 may access data stored in a secure datacontainer 528 in the managed partition 510 of the mobile device 502. Thedata secured in the secure data container may be accessed by the securenative applications 514, secure remote applications 522 executed by asecure application launcher 518, virtualization applications 526executed by a secure application launcher 518, and the like. The datastored in the secure data container 528 may include files, databases,and the like. The data stored in the secure data container 528 mayinclude data restricted to a specific secure application 530, sharedamong secure applications 532, and the like. Data restricted to a secureapplication may include secure general data 534 and highly secure data538. Secure general data may use a strong form of encryption such asAdvanced Encryption Standard (AES) 128-bit encryption or the like, whilehighly secure data 538 may use a very strong form of encryption such asAES 256-bit encryption. Data stored in the secure data container 528 maybe deleted from the mobile device 502 upon receipt of a command from thedevice manager 524. The secure applications (e.g., 514, 522, and 526)may have a dual-mode option 540. The dual mode option 540 may presentthe user with an option to operate the secured application in anunsecured or unmanaged mode. In an unsecured or unmanaged mode, thesecure applications may access data stored in an unsecured datacontainer 542 on the unmanaged partition 512 of the mobile device 502.The data stored in an unsecured data container may be personal data 544.The data stored in an unsecured data container 542 may also be accessedby unsecured applications 546 that are running on the unmanagedpartition 512 of the mobile device 502. The data stored in an unsecureddata container 542 may remain on the mobile device 502 when the datastored in the secure data container 528 is deleted from the mobiledevice 502. An enterprise may want to delete from the mobile device 502selected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The mobile device 502 may connect to enterprise resources 504 andenterprise services 508 at an enterprise, to the public Internet 548,and the like. The mobile device 502 may connect to enterprise resources504 and enterprise services 508 through virtual private networkconnections. The virtual private network connections, also referred toas microVPN or application-specific VPN, may be specific to particularapplications (as illustrated by microVPNs 550, particular devices,particular secured areas on the mobile device (as illustrated by O/S VPN552), and the like. For example, each of the wrapped applications in thesecured area of the mobile device 502 may access enterprise resourcesthrough an application specific VPN such that access to the VPN would begranted based on attributes associated with the application, possibly inconjunction with user or device attribute information. The virtualprivate network connections may carry Microsoft Exchange traffic,Microsoft Active Directory traffic, HyperText Transfer Protocol (HTTP)traffic, HyperText Transfer Protocol Secure (HTTPS) traffic, applicationmanagement traffic, and the like. The virtual private networkconnections may support and enable single-sign-on authenticationprocesses 554. The single-sign-on processes may allow a user to providea single set of authentication credentials, which are then verified byan authentication service 558. The authentication service 558 may thengrant to the user access to multiple enterprise resources 504, withoutrequiring the user to provide authentication credentials to eachindividual enterprise resource 504.

The virtual private network connections may be established and managedby an access gateway 560. The access gateway 560 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 504 to the mobile device 502. The access gateway560 may also re-route traffic from the mobile device 502 to the publicInternet 548, enabling the mobile device 502 to access publiclyavailable and unsecured applications that run on the public Internet548. The mobile device 502 may connect to the access gateway 560 via atransport network 562. The transport network 562 may use one or moretransport protocols and may be a wired network, wireless network, cloudnetwork, local area network, metropolitan area network, wide areanetwork, public network, private network, and the like.

The enterprise resources 504 may include email servers, file sharingservers, SaaS applications, Web application servers, Windows applicationservers, and the like. Email servers may include Exchange servers, LotusNotes servers, and the like. File sharing servers may include ShareFileservers, and the like. SaaS applications may include Salesforce, and thelike. Windows application servers may include any application serverthat is built to provide applications that are intended to run on alocal Windows operating system, and the like. The enterprise resources504 may be premise-based resources, cloud-based resources, and the like.The enterprise resources 504 may be accessed by the mobile device 502directly or through the access gateway 560. The enterprise resources 504may be accessed by the mobile device 502 via the transport network 562.

The enterprise services 508 may include authentication services 558,threat detection services 564, device manager services 524, file sharingservices 568, policy manager services 570, social integration services572, application controller services 574, and the like. Authenticationservices 558 may include user authentication services, deviceauthentication services, application authentication services, dataauthentication services, and the like. Authentication services 558 mayuse certificates. The certificates may be stored on the mobile device502, by the enterprise resources 504, and the like. The certificatesstored on the mobile device 502 may be stored in an encrypted locationon the mobile device 502, the certificate may be temporarily stored onthe mobile device 502 for use at the time of authentication, and thelike. Threat detection services 564 may include intrusion detectionservices, unauthorized access attempt detection services, and the like.Unauthorized access attempt detection services may include unauthorizedattempts to access devices, applications, data, and the like. Devicemanagement services 524 may include configuration, provisioning,security, support, monitoring, reporting, and decommissioning services.File sharing services 568 may include file management services, filestorage services, file collaboration services, and the like. Policymanager services 570 may include device policy manager services,application policy manager services, data policy manager services, andthe like. Social integration services 572 may include contactintegration services, collaboration services, integration with socialnetworks such as Facebook, Twitter, and LinkedIn, and the like.Application controller services 574 may include management services,provisioning services, deployment services, assignment services,revocation services, wrapping services, and the like.

The enterprise mobility technical architecture 500 may include anapplication store 578. The application store 578 may include unwrappedapplications 580, pre-wrapped applications 582, and the like.Applications may be populated in the application store 578 from theapplication controller 574. The application store 578 may be accessed bythe mobile device 502 through the access gateway 560, through the publicInternet 548, or the like. The application store 578 may be providedwith an intuitive and easy to use user interface.

A software development kit 584 may provide a user the capability tosecure applications selected by the user by wrapping the application asdescribed previously in this description. An application that has beenwrapped using the software development kit 584 may then be madeavailable to the mobile device 502 by populating it in the applicationstore 578 using the application controller 574.

The enterprise mobility technical architecture 500 may include amanagement and analytics capability 588. The management and analyticscapability 588 may provide information related to how resources areused, how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 6 is another illustrative enterprise mobility management system600. Some of the components of the mobility management system 500described above with reference to FIG. 5 have been omitted for the sakeof simplicity. The architecture of the system 600 depicted in FIG. 6 issimilar in many respects to the architecture of the system 500 describedabove with reference to FIG. 5 and may include additional features notmentioned above.

In this case, the left hand side represents an enrolled mobile device602 with a client agent 604, which interacts with gateway server 606(which includes Access Gateway and application controller functionality)to access various enterprise resources 608 and services 609 such asExchange, Sharepoint, public-key infrastructure (PKI) Resources,Kerberos Resources, Certificate Issuance service, as shown on the righthand side above. Although not specifically shown, the mobile device 602may also interact with an enterprise application store (StoreFront) forthe selection and downloading of applications.

The client agent 604 acts as the UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the High-Definition User Experience (HDX)/ICA displayremoting protocol. The client agent 604 also supports the installationand management of native applications on the mobile device 602, such asnative iOS or Android applications. For example, the managedapplications 610 (mail, browser, wrapped application) shown in thefigure above are all native applications that execute locally on themobile device 602. Client agent 604 and application management frameworkof this architecture act to provide policy driven managementcapabilities and features such as connectivity and SSO (single sign on)to enterprise resources/services 608. The client agent 604 handlesprimary user authentication to the enterprise, normally to AccessGateway (AG) 606 with SSO to other gateway server components. The clientagent 604 obtains policies from gateway server 606 to control thebehavior of the managed applications 610 on the mobile device 602.

The Secure InterProcess Communication (IPC) links 612 between the nativeapplications 610 and client agent 604 represent a management channel,which may allow a client agent to supply policies to be enforced by theapplication management framework 614 “wrapping” each application. TheIPC channel 612 may also allow client agent 604 to supply credential andauthentication information that enables connectivity and SSO toenterprise resources 608. Finally, the IPC channel 612 may allow theapplication management framework 614 to invoke user interface functionsimplemented by client agent 604, such as online and offlineauthentication.

Communications between the client agent 604 and gateway server 606 areessentially an extension of the management channel from the applicationmanagement framework 614 wrapping each native managed application 610.The application management framework 614 may request policy informationfrom client agent 604, which in turn may request it from gateway server606. The application management framework 614 may requestauthentication, and client agent 604 may log into the gateway servicespart of gateway server 606 (also known as NETSCALER ACCESS GATEWAY).Client agent 604 may also call supporting services on gateway server606, which may produce input material to derive encryption keys for thelocal data vaults 616, or may provide client certificates which mayenable direct authentication to PKI protected resources, as more fullyexplained below.

In more detail, the application management framework 614 “wraps” eachmanaged application 610. This may be incorporated via an explicit buildstep, or via a post-build processing step. The application managementframework 614 may “pair” with client agent 604 on first launch of anapplication 610 to initialize the Secure IPC channel 612 and obtain thepolicy for that application. The application management framework 614may enforce relevant portions of the policy that apply locally, such asthe client agent login dependencies and some of the containment policiesthat restrict how local OS services may be used, or how they mayinteract with the managed application 610.

The application management framework 614 may use services provided byclient agent 604 over the Secure IPC channel 612 to facilitateauthentication and internal network access. Key management for theprivate and shared data vaults 616 (containers) may be also managed byappropriate interactions between the managed applications 610 and clientagent 604. Vaults 616 may be available only after online authentication,or may be made available after offline authentication if allowed bypolicy. First use of vaults 616 may require online authentication, andoffline access may be limited to at most the policy refresh periodbefore online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 610 through Access Gateway 606. The applicationmanagement framework 614 may be responsible for orchestrating thenetwork access on behalf of each managed application 610. Client agent604 may facilitate these network connections by providing suitable timelimited secondary credentials obtained following online authentication.Multiple modes of network connection may be used, such as reverse webproxy connections and end-to-end VPN-style tunnels 618.

The Mail and Browser managed applications 610 have special status andmay make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the Mail application 610may use a special background network access mechanism that allows it toaccess an Exchange server 608 over an extended period of time withoutrequiring a full AG logon. The Browser application 610 may use multipleprivate data vaults 616 to segregate different kinds of data.

This architecture may support the incorporation of various othersecurity features. For example, gateway server 606 (including itsgateway services) in some cases may not need to validate activedirectory (AD) passwords. It can be left to the discretion of anenterprise whether an AD password may be used as an authenticationfactor for some users in some situations. Different authenticationmethods may be used if a user is online or offline (i.e., connected ornot connected to a network).

Step up authentication is a feature wherein gateway server 606 mayidentify managed native applications 610 that are allowed to have accessto highly classified data requiring strong authentication, and ensurethat access to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequired by the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 616 (containers) on the mobile device 602. The vaults 616 may beencrypted so that all on-device data including files, databases, andconfigurations are protected. For on-line vaults, the keys may be storedon the server (gateway server 606), and for off-line vaults, a localcopy of the keys may be protected by a user password or biometricvalidation. If or when data is stored locally on the mobile device 602in the secure container 616, it may be preferred that a minimum of AES256 encryption algorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein security events happeninginside a managed application 610 may be logged and reported to thebackend. Data wiping may be supported, such as if or when the managedapplication 610 detects tampering, associated encryption keys may bewritten over with random data, leaving no hint on the file system thatuser data was destroyed. Screenshot protection may be another feature,where an application may prevent any data from being stored inscreenshots. For example, the key window's hidden property may be set toYES. This may cause whatever content is currently displayed on thescreen to be hidden, resulting in a blank screenshot where any contentwould normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the mobile device602 is generated using a passphrase or biometric data supplied by theuser (if offline access is required). It may be XORed with another keyrandomly generated and stored on the server side if offline access isnot required. Key Derivation functions may operate such that keysgenerated from the user password use KDFs (key derivation functions,notably Password-Based Key Derivation Function 2 (PBKDF2)) rather thancreating a cryptographic hash of it. The latter makes a key susceptibleto brute force or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector will cause multiple copies of the sameencrypted data to yield different cipher text output, preventing bothreplay and cryptanalytic attacks. This will also prevent an attackerfrom decrypting any data even with a stolen encryption key. Further,authentication then decryption may be used, wherein application data isdecrypted only after the user has authenticated within the application.Another feature may relate to sensitive data in memory, which may bekept in memory (and not in disk) only when it is needed. For example,login credentials may be wiped from memory after login, and encryptionkeys and other data inside objective-C instance variables are notstored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented, wherein after a policy-definedperiod of inactivity, a user session is terminated.

Data leakage from the application management framework 614 may beprevented in other ways. For example, if or when a managed application610 is put in the background, the memory may be cleared after apredetermined (configurable) time period. When backgrounded, a snapshotmay be taken of the last displayed screen of the application to fastenthe foregrounding process. The screenshot may contain confidential dataand hence should be cleared.

Another security feature may relate to the use of an OTP (one timepassword) 620 without the use of an AD (active directory) 622 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 620 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text may be sent to the user with an OTP 620. In some cases,this may be implemented only for online use, with a prompt being asingle field.

An offline password may be implemented for offline authentication forthose managed applications 610 for which offline use is permitted viaenterprise policy. For example, an enterprise may want StoreFront to beaccessed in this manner. In this case, the client agent 604 may requirethe user to set a custom offline password and the AD password is notused. Gateway server 606 may provide policies to control and enforcepassword standards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature may relate to the enablement of a client sidecertificate for certain applications 610 as secondary credentials (forthe purpose of accessing PKI protected web resources via the applicationmanagement framework micro VPN feature). For example, a managedapplication 610 may utilize such a certificate. In this case,certificate-based authentication using ActiveSync protocol may besupported, wherein a certificate from the client agent 604 may beretrieved by gateway server 606 and used in a keychain. Each managedapplication 610 may have one associated client certificate, identifiedby a label that is defined in gateway server 606.

Gateway server 606 may interact with an enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The client agent 604 and the application management framework 614 may beenhanced to support obtaining and using client certificates forauthentication to internal PKI protected network resources. More thanone certificate may be supported, such as to match various levels ofsecurity and/or separation requirements. The certificates may be used bythe Mail and Browser managed applications 610, and ultimately byarbitrary wrapped applications 610 (provided those applications use webservice style communication patterns where it is reasonable for theapplication management framework to mediate HTTPS requests).

Application management client certificate support on iOS may rely onimporting a public-key cryptography standards (PKCS) 12 BLOB (BinaryLarge Object) into the iOS keychain in each managed application 610 foreach period of use. Application management framework client certificatesupport may use a HTTPS implementation with private in-memory keystorage. The client certificate may not be present in the iOS keychainand may not be persisted except potentially in “online-only” data valuethat is strongly protected.

Mutual SSL or TLS may also be implemented to provide additional securityby requiring that a mobile device 602 is authenticated to theenterprise, and vice versa. Virtual smart cards for authentication togateway server 606 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toActive Directory (AD) 622, using an AD password or trusted clientcertificate, and obtain Kerberos service tickets to respond to HTTPNegotiate authentication challenges. The limited support feature relatesto constrained delegation in Citrix Access Gateway Enterprise Edition(AGEE), where AGEE supports invoking Kerberos protocol transition so itcan obtain and use Kerberos service tickets (subject to constraineddelegation) in response to HTTP Negotiate authentication challenges.This mechanism works in reverse web proxy (aka corporate virtual privatenetwork (CVPN)) mode, and when HTTP (but not HTTPS) connections areproxied in VPN and MicroVPN mode.

Another feature may relate to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may include aremote wipe functionality even when a managed application 610 is notrunning.

A multi-site architecture or configuration of enterprise applicationstore and an application controller may be supported that allows usersto be serviced from one of several different locations in case offailure.

In some cases, managed applications 610 may be allowed to access acertificate and private key via an API (for example, OpenSSL). Trustedmanaged applications 610 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as if or when an application behaves like a browserand no certificate access is required, if or when an application reads acertificate for “who am I,” if or when an application uses thecertificate to build a secure session token, and if or when anapplication uses private keys for digital signing of important data(e.g. transaction log) or for temporary data encryption.

Deploying and Implementing Enterprise Policies that Control AugmentedReality Computing Functions

FIG. 7 depicts an illustrative computing environment for deploying andimplementing enterprise policies that control augmented realitycomputing functions in accordance with one or more illustrative aspectsdescribed herein. Referring to FIG. 7, computing environment 700 mayinclude an enterprise user computing device 710, an endpoint managementcomputing platform 720, an rendering service computing platform 730, anadministrator computing device 740, and a network 750. Enterprise usercomputing device 710, endpoint management computing platform 720,rendering service computing platform 730, and administrator computingdevice 740 may include one or more physical components, such as one ormore processors, memories, communication interfaces, and/or the like. Insome instances, enterprise user computing device 710 and administratorcomputing device 740 may include, incorporate, and/or implement one ormore aspects of the client devices, mobile devices, and/or user devicesdiscussed above. Endpoint management computing platform 720 andrendering service computing platform 730 may include, incorporate,and/or implement one or more aspects of the enterprise systems and/ormanagement servers discussed above. Additionally or alternatively,endpoint management computing platform 720 and rendering servicecomputing platform 730 may include, incorporate, and/or implement one ormore aspects of the virtualization servers and/or other virtualizationinfrastructure discussed above and/or may communicate with one or moreenterprise systems that include, incorporate, and/or implement one ormore aspects of the virtualization servers and/or other virtualizationinfrastructure discussed above.

For example, enterprise user computing device 710 may include at leastone processor 711, at least one memory 712, and at least onecommunication interface 714. Processor 711 may execute instructionsstored in memory 712 that cause enterprise user computing device 710 toperform one or more functions, such as receiving and implementingenterprise policies (which may, e.g., be received from endpointmanagement computing platform 720), intercepting requests to captureviews presented by enterprise user computing device 710, and selectivelystoring view information having augmented elements and/or preventing thecapturing of such view information based on the enterprise policies, asdescribed in greater detail below. Memory 712 may store at least oneenterprise application 713, which may include instructions that enableand/or cause enterprise user computing device 710 to display and/orotherwise present one or more graphical user interfaces and/or otherviews having augmented elements. Communication interface 714 may includeone or more network interfaces via which enterprise user computingdevice 710 may communicate with one or more other systems and/or devicesin computing environment 700, such as endpoint management computingplatform 720, rendering service computing platform 730, administratorcomputing device 740, and/or one or more other systems and/or devices.

Endpoint management computing platform 720 may be a server computersystem that is associated with an enterprise organization. For instance,endpoint management computing platform 720 may include one or morecomputing devices that are configured to perform one or more computingfunctions, such as creating and managing device enrollment data,enterprise policy data, and/or other enterprise data for various userdevices (e.g., enterprise user computing device 710). Rendering servicecomputing platform 730 also may be a server computer system that isassociated with an enterprise organization. For instance, renderingservice computing platform 730 may include one or more computing devicesthat are configured to perform one or more computing functions, such asreceiving real-world view information from various user devices (e.g.,enterprise user computing device 710), rendering mesh elements based onreceived view information, and/or providing rendered mesh elements tovarious user devices (e.g., enterprise user computing device 710).

Administrator computing device 740 may be a user computing device thatis used by an administrative user (who may, e.g., be associated with anenterprise organization that operates, configures, and/or uses endpointmanagement computing platform 720 and/or rendering service computingplatform 730, and who may be different from the user of enterprise usercomputing device 710). For instance, the administrative user ofadministrator computing device 740 may be a network administrator withsupervisory access rights that include rights to establish enterprisepolicies, to approve and/or deny policy variance requests, and/or tootherwise manage an enterprise computing environment, as illustrated ingreater detail below. Network 750 may include one or more local areanetworks, wide area networks, public networks, private networks, and/orsub-networks and may interconnect enterprise user computing device 710,endpoint management computing platform 720, rendering service computingplatform 730, and/or administrator computing device 740.

FIGS. 8A-8C depict an example event sequence for deploying andimplementing enterprise policies that control augmented realitycomputing functions in accordance with one or more illustrative aspectsdescribed herein. Referring to FIG. 8A, at step 801, endpoint managementcomputing platform 720 may receive policy configuration information(e.g., from administrator computing device 740). For instance, endpointmanagement computing platform 720 may receive policy configurationinformation from administrator computing device 740 defining one or moreenterprise policies to be enforced on and/or otherwise implemented withrespect to one or more enrolled devices (which may, e.g., be managed byendpoint management computing platform 720 and enrolled in a mobiledevice management scheme deployed by an enterprise organizationoperating endpoint management computing platform 720).

At step 802, endpoint management computing platform 720 may generateenterprise policy information. For example, at step 802, endpointmanagement computing platform 720 may generate enterprise policyinformation based on the policy configuration information received fromadministrator computing device 740. The enterprise policy informationgenerated by endpoint management computing platform 720 may, forinstance, include one or more augmented capture policies (which may,e.g., control capturing of augmented renderings, as discussed in greaterdetail below) and/or other enterprise management information, such asother policy information defining other policy rules, deviceprovisioning information, enrollment certificates, and/or otherinformation.

At step 803, endpoint management computing platform 720 may send theenterprise policy information to enterprise user computing device 710.For instance, at step 803, endpoint management computing platform 720may send any and/or all of the enterprise policy information discussedin the previous example to enterprise user computing device 710, whichmay cause enterprise user computing device 710 and/or a client agent(e.g., client agent 604) executing on enterprise user computing device710 to implement one or more mobile device management policies and/orexecute other commands and/or functions based on the policy informationreceived from endpoint management computing platform 720.

At step 804, enterprise user computing device 710 may receive theenterprise policy information from endpoint management computingplatform 720. For example, at step 804, enterprise user computing device710 may receive, via the communication interface (e.g., communicationinterface 714), enterprise policy information defining one or moreenterprise policies that, when implemented, control capture of one ormore augmented renderings on the enterprise user computing device (e.g.,enterprise user computing device 710). For instance, the enterprisepolicy information received by enterprise user computing device 710 atstep 804 may define one or more enterprise policies that, whenimplemented, selectively allow and/or prohibit enterprise user computingdevice 710 from capturing still images and/or video recordings of viewshaving augmented renderings presented on enterprise user computingdevice 710 in all and/or specific circumstances. For instance, the oneor more enterprise policies may selectively allow and/or prohibitenterprise user computing device 710 from capturing still images and/orvideo recordings of views having augmented renderings presented onenterprise user computing device 710 when enterprise user computingdevice 710 is located in specific geographic locations, when enterpriseuser computing device 710 is located in specific network locations, whenenterprise user computing device 710 is being used during specific timesand/or on specific days, when enterprise user computing device 710 isrunning specific applications, and/or the like.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receiving theenterprise policy information defining the one or more enterprisepolicies from an endpoint management computing platform that manages apolicy deployment associated with an enterprise organization. Forexample, in receiving the enterprise policy information defining the oneor more enterprise policies at step 204, enterprise user computingdevice 710 may receive the enterprise policy information defining theone or more enterprise policies from an endpoint management computingplatform (e.g., endpoint management computing platform 720) that managesa policy deployment associated with an enterprise organization.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, prohibits capture of at least one augmented rendering onthe enterprise user computing device. For example, in receiving theenterprise policy information defining the one or more enterprisepolicies at step 204, enterprise user computing device 710 may receiveinformation defining at least one enterprise policy that, whenimplemented, prohibits capture of at least one augmented rendering onthe enterprise user computing device (e.g., enterprise user computingdevice 710). For instance, enterprise user computing device 710 mayreceive information defining at least one enterprise policy that, whenimplemented, prohibits capture of augmented renderings (which may, e.g.,include a combination of augmented reality elements and real worldelements) on enterprise user computing device 710 in all circumstances.Additionally or alternatively, enterprise user computing device 710 mayreceive information defining at least one enterprise policy that, whenimplemented, prohibits capture of augmented renderings (which may, e.g.,include a combination of augmented reality elements and real worldelements) on enterprise user computing device 710 in specificcircumstances, such as when enterprise user computing device 710 islocated in specific geographic locations, when enterprise user computingdevice 710 is located in specific network locations, when enterpriseuser computing device 710 is being used during specific times and/or onspecific days, when enterprise user computing device 710 is runningspecific applications, and/or the like.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, prohibits capture of real-world elements associated with atleast one augmented rendering on the enterprise user computing device.For example, in receiving the enterprise policy information defining theone or more enterprise policies at step 204, enterprise user computingdevice 710 may receive information defining at least one enterprisepolicy that, when implemented, prohibits capture of real-world elementsassociated with at least one augmented rendering on the enterprise usercomputing device (e.g., enterprise user computing device 710). Forinstance, enterprise user computing device 710 may receive informationdefining at least one enterprise policy that, when implemented,prohibits capture of real-world elements associated with augmentedrenderings (which may, e.g., include a combination of augmented realityelements and real world elements) on enterprise user computing device710 in all circumstances. Additionally or alternatively, enterprise usercomputing device 710 may receive information defining at least oneenterprise policy that, when implemented, prohibits capture ofreal-world elements associated with augmented renderings (which may,e.g., include a combination of augmented reality elements and real worldelements) on enterprise user computing device 710 in specificcircumstances, such as when enterprise user computing device 710 islocated in specific geographic locations, when enterprise user computingdevice 710 is located in specific network locations, when enterpriseuser computing device 710 is being used during specific times and/or onspecific days, when enterprise user computing device 710 is runningspecific applications, and/or the like.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, prohibits capture of augmented elements associated with atleast one augmented rendering on the enterprise user computing device.For example, in receiving the enterprise policy information defining theone or more enterprise policies at step 204, enterprise user computingdevice 710 may receive information defining at least one enterprisepolicy that, when implemented, prohibits capture of augmented elementsassociated with at least one augmented rendering on the enterprise usercomputing device (e.g., enterprise user computing device 710). Forinstance, enterprise user computing device 710 may receive informationdefining at least one enterprise policy that, when implemented,prohibits capture of augmented reality elements associated withaugmented renderings (which may, e.g., include a combination ofaugmented reality elements and real world elements) on enterprise usercomputing device 710 in all circumstances. Additionally oralternatively, enterprise user computing device 710 may receiveinformation defining at least one enterprise policy that, whenimplemented, prohibits capture of augmented reality elements associatedwith augmented renderings (which may, e.g., include a combination ofaugmented reality elements and real world elements) on enterprise usercomputing device 710 in specific circumstances, such as when enterpriseuser computing device 710 is located in specific geographic locations,when enterprise user computing device 710 is located in specific networklocations, when enterprise user computing device 710 is being usedduring specific times and/or on specific days, when enterprise usercomputing device 710 is running specific applications, and/or the like.

In some embodiments, receiving the enterprise policy informationdefining the one or more enterprise policies may include receivinginformation defining at least one enterprise policy that, whenimplemented, allows capture of mesh elements associated with at leastone augmented rendering on the enterprise user computing device. Forexample, in receiving the enterprise policy information defining the oneor more enterprise policies at step 204, enterprise user computingdevice 710 may receive information defining at least one enterprisepolicy that, when implemented, allows capture of mesh elementsassociated with at least one augmented rendering on the enterprise usercomputing device (e.g., enterprise user computing device 710). Forinstance, enterprise user computing device 710 may receive informationdefining at least one enterprise policy that, when implemented, allowscapture of mesh elements associated with augmented renderings (whichmay, e.g., include a combination of augmented reality elements and realworld elements, as well as mesh elements) on enterprise user computingdevice 710 in all circumstances. Additionally or alternatively,enterprise user computing device 710 may receive information defining atleast one enterprise policy that, when implemented, allows capture ofmesh elements associated with augmented renderings (which may, e.g.,include a combination of augmented reality elements and real worldelements, as well as mesh elements) on enterprise user computing device710 in specific circumstances, such as when enterprise user computingdevice 710 is located in specific geographic locations, when enterpriseuser computing device 710 is located in specific network locations, whenenterprise user computing device 710 is being used during specific timesand/or on specific days, when enterprise user computing device 710 isrunning specific applications, and/or the like.

Referring to FIG. 8B, at step 805, enterprise user computing device 710may implement one or more policies (e.g., based on the policyinformation received from endpoint management computing platform 720).For example, at step 805, enterprise user computing device 710 mayimplement one or more policies by storing enterprise policy informationand/or other provisioning information, one or more device enrollmentcertificates, and/or other information received from endpoint managementcomputing platform 720. Additionally or alternatively, enterprise usercomputing device 710 may implement one or more policies by configuring aclient agent (e.g., client agent 604) on enterprise user computingdevice 710 and/or one or more wrapped applications on enterprise usercomputing device 710 based on the policy information received fromendpoint management computing platform 720.

At step 806, enterprise user computing device 710 may receive inputrequesting to open an application. For example, at step 806, enterpriseuser computing device 710 may receive input from a user of enterpriseuser computing device 710 requesting to open an enterprise application.At step 807, enterprise user computing device 710 may launch anapplication (e.g., based on the input received at step 806). Forexample, at step 807, enterprise user computing device 710 may launch anenterprise application (e.g., enterprise application 713) which mayinclude one or more augmented reality features and/or spatial computingfunctions.

At step 808, enterprise user computing device 710 may receive inputrequesting to capture a view associated with the application. Forexample, at step 808, enterprise user computing device 710 may receiveinput from the user of enterprise user computing device 710 requestingto capture a still image and/or a video recording of one or more viewsbeing displayed and/or otherwise presented by the enterprise application(e.g., enterprise application 713). In addition, such views may, forinstance, include one or more augmented reality elements (which may,e.g., be generated by and/or otherwise associated with enterpriseapplication 713).

Referring to FIG. 8C, at step 809, enterprise user computing device 710may intercept the request to capture the view. For example, at step 809,after receiving the enterprise policy information defining the one ormore enterprise policies, enterprise user computing device 710 mayintercept a request to capture at least one view presented by theenterprise user computing device (e.g., enterprise user computing device710), and the at least one view may include at least one augmentedreality element. For instance, enterprise user computing device 710 mayintercept a request to capture a still image and/or a video recording ofat least one view presented by the enterprise user computing device(e.g., enterprise user computing device 710) that includes one or moreaugmented reality elements.

In some embodiments, intercepting the request to capture the at leastone view presented by the enterprise user computing device may includeintercepting the request to capture the at least one view presented bythe enterprise user computing device from an operating system executingon the enterprise user computing device. For example, in interceptingthe request to capture the at least one view presented by the enterpriseuser computing device (e.g., enterprise user computing device 710),enterprise user computing device 710 may intercept the request tocapture the at least one view presented by the enterprise user computingdevice (e.g., enterprise user computing device 710) from an operatingsystem executing on the enterprise user computing device (e.g.,enterprise user computing device 710). For instance, enterprise usercomputing device 710 and/or a client agent (e.g., client agent 604)executing on enterprise user computing device 710 may listen for ascreenshot notification and/or a screen recording notification, whichmay be intercepted at step 809. For instance, on an IOS device,enterprise user computing device 710 and/or a client agent (e.g., clientagent 604) executing on enterprise user computing device 710 may listenfor a UIApplicationUserDidTakeScreenshotNotification. On an ANDROIDdevice, enterprise user computing device 710 and/or a client agent(e.g., client agent 604) executing on enterprise user computing device710 may add a FileObserver or ContentObserver to listen for andintercept the request to capture the view(s).

In some embodiments, intercepting the request to capture the at leastone view presented by the enterprise user computing device may includeintercepting the request to capture the at least one view presented bythe enterprise user computing device from an enterprise applicationexecuting on the enterprise user computing device. For example, inintercepting the request to capture the at least one view presented bythe enterprise user computing device (e.g., enterprise user computingdevice 710), enterprise user computing device 710 may intercept therequest to capture the at least one view presented by the enterpriseuser computing device (e.g., enterprise user computing device 710) froman enterprise application (e.g., enterprise application 713) executingon the enterprise user computing device (e.g., enterprise user computingdevice 710). For instance, the enterprise application (e.g., enterpriseapplication 713) may be a wrapped application and/or may utilize aspecific software development kit (SDK) that implements a managementframework (e.g., management framework 614), and the request to capturethe view(s) may be intercepted by the application's wrapper and/or bythe management framework. For example, the application may be managedthrough hooking the operating system's application programminginterfaces (APIs), injecting code into the application, methodswizzling, and/or by other techniques, and when the application executesa function call to capture a screenshot or video recording at theapplication layer, that function call may be intercepted at the policymanagement layer (which may, e.g., be provided by the SDK and/or themanagement framework).

At step 810, enterprise user computing device 710 may determine whetherone or more policies being applied on enterprise user computing device710 allow for capture of views comprising augmented reality elements.For example, at step 810, in response to intercepting the request tocapture the at least one view presented by the enterprise user computingdevice (e.g., enterprise user computing device 710), enterprise usercomputing device 710 may determine whether the one or more enterprisepolicies allow capture of views comprising augmented reality elements.For instance, enterprise user computing device 710 and/or a client agent(e.g., client agent 604) executing on enterprise user computing device710 may evaluate one or more parameters of the request (e.g., the typeof content included in the view, the device's current geographiclocation, the device's current network location, the current time ofday, the applications currently running on the device, etc.) againstcorresponding parameters of one or more enterprise policies beingapplied on the device (e.g., the one or more policies received at step804 and/or implemented at step 805 and/or other policies being enforcedon the device) to identify whether the view can be captured as-is,whether a modified version of the view can be captured (e.g., asdiscussed below), or whether the view cannot be captured at all. Basedon evaluating the parameters of the request against correspondingparameters of these policies, enterprise user computing device 710 mayproceed as illustrated in FIG. 8C and as described below.

If enterprise user computing device 710 determines at step 810 that theone or more policies being applied on enterprise user computing device710 allow for capture (e.g., either of the currently presented view orof a modified version of the currently presented view), then at step811, enterprise user computing device 710 may store view information.For example, at step 811, based on determining that the one or moreenterprise policies allow capture of views comprising augmented realityelements, enterprise user computing device 710 may store viewinformation associated with the at least one view comprising the atleast one augmented reality element. For instance, enterprise usercomputing device 710 may display and/or otherwise present a graphicaluser interface similar to graphical user interface 900, which isillustrated in FIG. 9. As seen in FIG. 9, graphical user interface 900may include real-world elements and augmented reality elements. Instoring view information at step 811, enterprise user computing device710 may store still image data and/or video recording data correspondingto the real-world elements and the augmented reality elements includedin graphical user interface 900 and/or other data associated with theview being presented by enterprise user computing device 710.

In some embodiments, storing the view information associated with the atleast one view comprising the at least one augmented reality element mayinclude: generating a modified view based on the at least one viewpresented by the enterprise user computing device; and storinginformation associated with the modified view generated based on the atleast one view presented by the enterprise user computing device. Forexample, in storing the view information associated with the at leastone view comprising the at least one augmented reality element at step811, enterprise user computing device 710 may generate a modified viewbased on the at least one view presented by the enterprise usercomputing device (e.g., enterprise user computing device 710). Inaddition, enterprise user computing device 710 may store informationassociated with the modified view generated based on the at least oneview presented by the enterprise user computing device (e.g., enterpriseuser computing device 710). For example, in instances in whichenterprise user computing device 710 determines, based on the one ormore enterprise policies being applied on the device, that a modifiedversion of the view can be captured but the actual view itself cannot becaptured, enterprise user computing device 710 may generate and store amodified view by removing and/or otherwise altering image data and/orvideo data corresponding to the current view being presented byenterprise user computing device 710, as described in greater detailbelow.

In some embodiments, generating the modified view based on the at leastone view presented by the enterprise user computing device may includeremoving one or more real-world elements from the at least one viewpresented by the enterprise user computing device. For example, ingenerating the modified view based on the at least one view presented bythe enterprise user computing device (e.g., enterprise user computingdevice 710), enterprise user computing device 710 may remove one or morereal-world elements from the at least one view presented by theenterprise user computing device (e.g., enterprise user computing device710). For instance, enterprise user computing device 710 may remove oneor more real-world elements from the at least one view based on the oneor more enterprise policies being applied on enterprise user computingdevice 710 prohibiting capture of such real-world elements (e.g., undercurrent operating conditions of enterprise user computing device 710).An example of the resulting modified view, which may then be stored byenterprise user computing device 710, is illustrated in graphical userinterface 1000, which is depicted in FIG. 10. As seen in FIG. 10,graphical user interface 1000 may include a modified view in which thereal-world elements from graphical user interface 900 (which may, e.g.,correspond to the original view presented by enterprise user computingdevice 710) have been removed and the augmented reality elements fromgraphical user interface 900 have been preserved. Another example of theresulting modified view, which may then be stored by enterprise usercomputing device 710, is illustrated in graphical user interface 1100,which is depicted in FIG. 11. As seen in FIG. 11, graphical userinterface 1100 may include a modified view in which the real-worldelements and the augmented reality elements from graphical userinterface 900 have been removed and mesh elements corresponding to theremoved real-world elements have been added. Such mesh elements may, forinstance, be rendered by enterprise user computing device 710 and/or byrendering service computing platform 730, as discussed in greater detailbelow.

In some embodiments, generating the modified view based on the at leastone view presented by the enterprise user computing device may includeremoving one or more augmented elements from the at least one viewpresented by the enterprise user computing device. For example, ingenerating the modified view based on the at least one view presented bythe enterprise user computing device (e.g., enterprise user computingdevice 710), enterprise user computing device 710 may remove one or moreaugmented elements from the at least one view presented by theenterprise user computing device (e.g., enterprise user computing device710). For instance, enterprise user computing device 710 may remove oneor more augmented reality elements from the at least one view based onthe one or more enterprise policies being applied on enterprise usercomputing device 710 prohibiting capture of such augmented realityelements (e.g., under current operating conditions of enterprise usercomputing device 710). An example of the resulting modified view, whichmay then be stored by enterprise user computing device 710, isillustrated in graphical user interface 1200, which is depicted in FIG.12. As seen in FIG. 12, graphical user interface 1200 may include amodified view in which the augmented reality elements from graphicaluser interface 900 (which may, e.g., correspond to the original viewpresented by enterprise user computing device 710) have been removed andthe real-world elements from graphical user interface 900 have beenpreserved. Another example of the resulting modified view, which maythen be stored by enterprise user computing device 710, is illustratedin graphical user interface 1300, which is depicted in FIG. 13. As seenin FIG. 13, graphical user interface 1300 may include a modified view inwhich the augmented reality elements from graphical user interface 900have been removed, the real-world elements from graphical user interface900 have been preserved, and mesh elements corresponding to thereal-world elements have been added. Such mesh elements may, forinstance, be rendered by enterprise user computing device 710 and/or byrendering service computing platform 730, as discussed in greater detailbelow.

In some embodiments, prior to storing the view information associatedwith the at least one view comprising the at least one augmented realityelement (e.g., at step 811), enterprise user computing device 710 mayrender one or more mesh elements associated with the at least one viewpresented by the enterprise user computing device (e.g., enterprise usercomputing device 710). For instance, enterprise user computing device710 may locally render such mesh elements, based on the real-worldelements included in the at least one view that is being captured, usingone or more object recognition and shape outlining algorithms (whichmay, e.g., be executed locally on enterprise user computing device 710).Subsequently, enterprise user computing device 710 may merge the one ormore mesh elements associated with the at least one view presented bythe enterprise user computing device (e.g., enterprise user computingdevice 710) with image data defining the at least one view presented bythe enterprise user computing device (e.g., enterprise user computingdevice 710) to produce the view information associated with the at leastone view comprising the at least one augmented reality element. Forinstance, enterprise user computing device 710 may merge the renderedmesh elements with the image data (which may, e.g., include thereal-world elements and/or the augmented reality elements) to producethe view information that is ultimately stored by enterprise usercomputing device 710. Examples of the mesh elements may be seen in FIGS.11 and 13, as described above, and the example illustrated in FIG. 13shows how the mesh elements may be merged with other elements (e.g.,real-world elements) included in the view being captured.

In some embodiments, prior to storing the view information associatedwith the at least one view comprising the at least one augmented realityelement (e.g., at step 811), enterprise user computing device 710 maysend, via the communication interface (e.g., communication interface714), to a rendering service computing platform (e.g., rendering servicecomputing platform 730), a request for rendered mesh informationassociated with the at least one view presented by the enterprise usercomputing device (e.g., enterprise user computing device 710). Forinstance, instead of locally rendering mesh elements, as in the exampleabove, enterprise user computing device 710 may send a request torendering service computing platform 730 to render such mesh elementsbased on the real-world elements included in the at least one view thatis being captured. In sending such a request to rendering servicecomputing platform 730, enterprise user computing device 710 may send,to rendering service computing platform 730, image data associated withthe still image and/or video recording corresponding to the at least oneview that is being captured. Subsequently, enterprise user computingdevice 710 may receive, via the communication interface (e.g.,communication interface 714), from the rendering service computingplatform (e.g., rendering service computing platform 730), meshinformation defining one or more mesh elements associated with the atleast one view presented by the enterprise user computing device (e.g.,enterprise user computing device 710). For instance, enterprise usercomputing device 710 may receive the rendered mesh elements fromrendering service computing platform 730 as image data, and such imagedata may be produced by rendering service computing platform 730 byapplying one or more object recognition and shape outlining algorithmsto the image data sent to rendering service computing platform 730 byenterprise user computing device 710. This remote rendering of meshelements may, for instance, be technologically beneficial in someinstances, as it may reduce the usage of processing resources, powerresources, and/or other resources on enterprise user computing device710 by offloading the computation and/or other generation of the meshelements to rendering service computing platform 730.

After receiving the mesh information from rendering service computingplatform 730, enterprise user computing device 710 may merge the meshinformation defining the one or more mesh elements associated with theat least one view presented by the enterprise user computing device(e.g., enterprise user computing device 710) with image data definingthe at least one view presented by the enterprise user computing device(e.g., enterprise user computing device 710) to produce the viewinformation associated with the at least one view comprising the atleast one augmented reality element. For instance, enterprise usercomputing device 710 may merge the rendered mesh elements with the imagedata (which may, e.g., include the real-world elements and/or theaugmented reality elements) to produce the view information that isultimately stored by enterprise user computing device 710. As notedabove, examples of the mesh elements may be seen in FIGS. 11 and 13, asdescribed above, and the example illustrated in FIG. 13 shows how themesh elements may be merged with other elements (e.g., real-worldelements) included in the view being captured.

If enterprise user computing device 710 determines at step 810 that theone or more policies being applied on enterprise user computing device710 do not allow for capture (e.g., either of the currently presentedview or of a modified version of the currently presented view), then atstep 812, enterprise user computing device 710 may prevent capturing ofview information. For example, at step 812, based on determining thatthe one or more enterprise policies do not allow capture of viewscomprising augmented reality elements, enterprise user computing device710 may prevent the at least one view comprising the at least oneaugmented reality element from being captured. For instance, enterpriseuser computing device 710 might display one or more error messages andmay restrict, disable, and/or otherwise halt the storing of any imagedata, video data, and/or other data associated with the at least oneview being presented by enterprise user computing device 710.

In some embodiments, preventing the at least one view comprising the atleast one augmented reality element from being captured may include:generating an error notification indicating that the one or moreenterprise policies do not allow capture of views comprising augmentedreality elements; and presenting the error notification indicating thatthe one or more enterprise policies do not allow capture of viewscomprising augmented reality elements. For example, in preventing the atleast one view comprising the at least one augmented reality elementfrom being captured at step 812, enterprise user computing device 710may generate an error notification indicating that the one or moreenterprise policies do not allow capture of views comprising augmentedreality elements. For instance, enterprise user computing device 710 maygenerate such a notification based on one or more error templatesmaintained by enterprise user computing device 710. Subsequently,enterprise user computing device 710 may present the error notificationindicating that the one or more enterprise policies do not allow captureof views comprising augmented reality elements. For instance, inpresenting the error notification indicating that the one or moreenterprise policies do not allow capture of views comprising augmentedreality elements, enterprise user computing device 710 may displayand/or otherwise present a graphical user interface similar to graphicaluser interface 1400, which is depicted in FIG. 14. As seen in FIG. 14,graphical user interface 1400 may include text and/or other informationindicating that the requested capture is being blocked by one or moreenterprise policies being applied on enterprise user computing device710 (e.g., “One or more mobile device management policies imposed byyour enterprise organization do not allow capture of views that includeaugmented reality elements”).

Subsequently, the example event sequence may end. In addition, one ormore steps of the example event sequence may be repeated (e.g., onenterprise user computing device 710 and/or other enterprise usercomputing devices associated with the enterprise organization) asenterprise policies are updated (e.g., by an administrative user ofadministrator computing device 740) and/or pushed to enterprise devices(e.g., by endpoint management computing platform 720) and/or asadditional capture requests are received in connection with the sameenterprise application (e.g., enterprise application 713) and/ordifferent applications.

FIG. 15 depicts an example method of deploying and implementingenterprise policies that control augmented reality computing functionsin accordance with one or more illustrative aspects described herein.Referring to FIG. 15, at step 1505, an enterprise user computing devicehaving at least one processor, a communication interface, and memory mayreceive, via the communication interface, enterprise policy informationdefining one or more enterprise policies that, when implemented, controlcapture of one or more augmented renderings on the enterprise usercomputing device. At step 1510, after receiving the enterprise policyinformation defining the one or more enterprise policies, the enterpriseuser computing device may intercept a request to capture at least oneview presented by the enterprise user computing device, and the at leastone view may include at least one augmented reality element. At step1515, in response to intercepting the request to capture the at leastone view presented by the enterprise user computing device, theenterprise user computing device may determine whether the one or moreenterprise policies allow capture of views comprising augmented realityelements. At step 1520, based on determining that the one or moreenterprise policies allow capture of views comprising augmented realityelements, the enterprise user computing device may store viewinformation associated with the at least one view comprising the atleast one augmented reality element. Additionally or alternatively, atstep 1525, based on determining that the one or more enterprise policiesdo not allow capture of views comprising augmented reality elements, theenterprise user computing device may prevent the at least one viewcomprising the at least one augmented reality element from beingcaptured.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims.

What is claimed is:
 1. A method comprising: receiving, by a manageddevice, a request to capture at least one view presented by the manageddevice comprising at least one augmented reality element, wherein themanaged device is subject to restrictions included within policyinformation defining one or more policies that, when implemented,control capture of one or more augmented renderings on the manageddevice; intercepting, by the managed device, the request; anddetermining, by the managed device, whether the one or more policiesallow capture of views comprising augmented reality elements.
 2. Themethod of claim 1, further comprising: based on determining that one ormore policies allow capture of views comprising augmented realityelements, store view information associated with the at least one viewcomprising the at least one augmented reality element.
 3. The method ofclaim 1, further comprising: based on determining that the one or morepolicies do not allow capture of views comprising augmented realityelements, prevent the at least one view comprising the at least oneaugmented reality element from being captured.
 4. The method of claim 1,wherein the managed device is subject to restrictions included withinthe policy information defining one or more policies that, whenimplemented, prohibit capture of at least one augmented rendering on themanaged device.
 5. The method of claim 1, wherein the managed device issubject to restrictions included within the policy information definingone or more policies that, when implemented, prohibit capture of one ormore real-world elements associated with at least one augmentedrendering on the managed device.
 6. The method of claim 1, wherein themanaged device is subject to restrictions included within the policyinformation defining one or more policies that, when implemented,prohibit capture of one or more augmented elements associated with atleast one augmented rendering on the managed device.
 7. The method ofclaim 1, wherein the managed device is subject to restrictions includedwithin the policy information defining one or more policies that, whenimplemented, control capture of one or more mesh elements associatedwith at least one augmented rendering on the managed device.
 8. Themethod of claim 1, wherein intercepting the request comprisesintercepting the request to capture at least one view presented by themanaged device from an operating system executing on the managed device.9. The method of claim 1, wherein intercepting the request comprisesintercepting the request to capture at least one view presented by themanaged device from an application executing on the managed device. 10.The method of claim 1, further comprising: generating a modified viewbased on the at least one view presented by the managed device.
 11. Themethod of claim 1, further comprising: storing view informationassociated with the at least one view comprising the at least oneaugmented reality element.
 12. The method of claim 10, whereingenerating a modified view based on the at least one view presented bythe managed device comprises removing one or more real-world elementsfrom the at least one view presented by the managed device.
 13. Themethod of claim 10, wherein generating a modified view based on the atleast one view presented by the managed device comprises removing one ormore augmented elements from the at least one view presented by themanaged device.
 14. The method of claim 1, further comprising: renderingone or more mesh elements associated with the at least one viewpresented by the managed device; and merging the one or more meshelements associated with the at least one view presented by the manageddevice with image data defining the at least one view presented by themanaged device to produce view information associated with the at leastone view comprising the at least one augmented reality element.
 15. Themethod of claim 1, further comprising: sending, to a rendering servicecomputing platform, a request for rendered mesh information associatedwith at least one view presented by the managed device; receiving, fromthe rendering service computing platform, mesh information defining oneor more mesh elements associated with the at least one view presented bythe managed device; and merging the mesh information defining the one ormore mesh elements associated with the at least one view presented bythe managed device with image data defining the at least one viewpresented by the managed device to produce view information associatedwith the at least one view comprising the at least one augments realityelement.
 16. A managed device comprising: at least one processor; andmemory storing computer-readable instructions that, when executed by theat least one processor, cause the managed device to: receive a requestto capture at least one view presented by the managed device comprisingat least one augmented reality element, wherein the managed device issubject to restrictions included within policy information defining oneor more policies that, when implemented, control capture of one or moreaugmented renderings on the managed device; intercept the request; anddetermine whether the one or more policies allow capture of viewscomprising augmented reality elements.
 17. The managed device of claim16, wherein the memory stores additional computer-readable instructionsthat, when executed by the at least one processor, cause the manageddevice to: based on determining that one or more policies allow captureof views comprising augmented reality elements, store view informationassociated with the at least one view comprising the at least oneaugmented reality element.
 18. The managed device of claim 16, whereinthe memory stores additional computer-readable instructions that, whenexecuted by the at least one processor, cause the managed device to:based on determining that one or more policies do not allow capture ofviews comprising augmented reality elements, prevent the at least oneview comprising the at least one augmented reality element from beingcaptured.
 19. The managed device of claim 16, wherein the managed deviceis subject to restrictions included within the policy informationdefining one or more policies that, when implemented, prohibit captureof one or more real-world elements associated with at least oneaugmented rendering on the managed device.
 20. One or morenon-transitory computer-readable media storing instructions that, whenexecuted by a managed device comprising at least one processor, causethe managed device to: receive a request to capture at least one viewpresented by the managed device comprising at least one augmentedreality element, wherein the managed device is subject to restrictionsincluded within policy information defining one or more policies that,when implemented, control capture of one or more augmented renderings onthe managed device; intercept the request; and determine whether the oneor more policies allow capture of views comprising augmented realityelements.